chore: bump actions to node 24 runtime#88
Open
adisivaprasad wants to merge 1 commit into
Open
Conversation
GitHub deprecated the Node 20 runtime for actions, emitting a deprecation warning on every workflow run. This bumps all actions to versions running on Node 24: - actions/setup-python v5.1.0 -> v6.2.0 (action.yml, user-facing) - actions/setup-python v5 -> v6 (CI workflows) - actions/checkout v4 -> v6 - astral-sh/ruff-action v3 -> v4 - codecov/codecov-action v3 -> v6 - googleapis/release-please-action v4.1.3 -> v5.0.0 - pypa/gh-action-pypi-publish v1.13.0 -> v1.14.0 (composite, bumped for parity) Node 24 actions require GitHub runner >= v2.327.1, already met by hosted runners. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GitHub deprecated the Node 20 runtime for actions, so every workflow run currently emits a "Node.js 20 actions are deprecated" warning — including for downstream users of
opensource-nepal/commitlint@v1, sinceaction.ymlpulls inactions/setup-python@v5.1.0(Node 20).This bumps every referenced action to a version running on Node 24:
actions/setup-pythonv5.1.0v6.2.0action.yml(user-facing)actions/setup-pythonv5v6ci.yaml,release-please.ymlactions/checkoutv4v6astral-sh/ruff-actionv3v4ci.yamlcodecov/codecov-actionv3v6ci.yamlgoogleapis/release-please-actionv4.1.3v5.0.0release-please.ymlpypa/gh-action-pypi-publishv1.13.0v1.14.0release-please.yml(composite — bumped for parity)After this change, the deprecation warning is eliminated for downstream consumers of
opensource-nepal/commitlint@v1(the user-facing surface) and for the repo's ownci.yaml/commitlint.yamlruns.Known residual warning (blocked on upstream)
pypa/gh-action-pypi-publish@v1.14.0is a composite action that internally callsactions/setup-python@v5.6.0(Node 20). This means the release-please workflow will still emit a Node 20 warning on release runs only — not on PRs or normal CI.v1.14.0is the latest available release (April 2026) and there's no open PR upstream tracking this; the residual warning will resolve whenpypa/gh-action-pypi-publishbumps their internalsetup-pythonreference.Compatibility notes
v2.327.1. Hosted runners are already past this.googleapis/release-please-actionv4 → v5: manifest-based config is now required; this repo already hasrelease-please-config.json+.release-please-manifest.json, so it should work without further changes. Worth eyeballing the next release-please run.astral-sh/ruff-actionv3 → v4: some input names changed, but the CI step here is invoked with no inputs, so no migration needed.codecov/codecov-actionv3 → v6: deprecatedfile/plugininputs; this repo only passestoken,fail_ci_if_error,verbose— all still supported.Test plan
main, release-please workflow runs without error (release-please-action v5, pypi-publish v1.14.0)